Skip to content

feat(bedrock): prompt for region on bedrock provider - #35787

Closed
OpeOginni wants to merge 1 commit into
anomalyco:devfrom
OpeOginni:feat/prompt-bedrock-region
Closed

feat(bedrock): prompt for region on bedrock provider#35787
OpeOginni wants to merge 1 commit into
anomalyco:devfrom
OpeOginni:feat/prompt-bedrock-region

Conversation

@OpeOginni

Copy link
Copy Markdown
Contributor

Issue for this PR

Closes #28834

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

  • Adds prompt for AWS region when trying to connect to the bedrock provider::This particularrly helps Desktop users who don't make use of the terminal to set ENV variables, they can simply set the region on the dialog.
  • Improve docs showing that the Region ENV is very important to set if using credentials.

The Flow:

  • If AWS_REGION env exists: no region prompt.
  • If AWS_REGION env is missing: prompt for required Bedrock region.
  • Region from the prompt is stored as auth metadata.

How did you verify your code works?

  • Tests and typechecks work
  • Tried the opencode auth login fro amazon bedrock, and also tried to connect to the provider on desktop, the region prompt showed up.

Screenshots / recordings

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Connecting to Grok On Desktop Using OAuth shows weird and incomplete instructions

1 participant